Don't allow null values to be passed to the `register` method of
`RuntimeJNIAccess` and `RuntimeReflection`. Since these are public APIs
GraalVM should either handle null values (by ignoring them in this case)
or throw a `NullPointerException` before creating an asynchronous task
to perform the registration in the analysis, which then results in
`NullPointerException`s being thrown later when it's no longer possible
to understand where the null value originate from.

(cherry picked from commit e6c12dd)

(cherry picked from commit d621dbd)

Not before the register methods, which can miss cases, nor later on in a runnable.

(cherry picked from commit f94551a)

(cherry picked from commit d996f32)

(cherry picked from commit 0ba6cc2)

`destination` is the classpath GraalVM creates from parsing the jar
files passed to it. The ordering of the entries in the classpath is
important. Jar files themselves should be added before the entries of
their corresponding "Class-Path" attributes.

At the same time we want to process the contents of
`META-INF/native-image` of the entries in the "Class-Path" before
processing the contents of `META-INF/native-image` of the jar itself.
This is required to ensure that the jar `META-INF/native-image` contents
can override those of the entries in its "Class-Path".

As a result I chose to optimistically add the path to the classpath (aka
`destination`) and remove it afterwards if deemed necessary.

Fixes oracle#7677

(cherry picked from commit 5c0bfba)

(cherry picked from commit e7ee334)

(cherry picked from commit 94ec1bc)